allow for queue specific visibility time out configuration #264
Conversation
|
@qhenkart This looks awesome, thank you! I will merge it shortly to be in the next release. |
Admiral-Piett
force-pushed
the
master
branch
from
cc2c103
to
a43d9fd
Compare
|
@Admiral-Piett thank you! I will do it right away |
|
@Admiral-Piett are you using an alternative to Gofmt? I'm seeing a lot of inconsistent spacing and unusual amount of auto format changes in the rebased PR |
|
@qhenkart No I'm not, but I am reformatting lots of files as I go. I think it will work itself out eventually, though I know it's an irritant to look at when you're reviewing. Also, I'm going to close this. I'm sorry - I didn't notice your response until I after I merged this one - #280. It should have been just a rebase of yours anyway. If there's anything I missed or anything I misrepresented let's talk? |
|
This was rebased and merged in an alternate PR: #280 |
Currently there can only be a single VisibilityTimeout configuration that affects all queues. However in real life situations, some queues process more complex data than others requiring queue specific VisibilityTimeout settings. This PR simply updates the configuration so that queue specific visibility timeouts are also accepted